Oracle® Insurance Rules Palette
The following information only applies when the Product structure is in use.
For the following entities, a Plan will inherit configuration defined in a Product- and/or Child Product-level override:
For example if “Product A” and “Plan A” are directly related to each other, and each has its own override of the PlanScreen business rule, the PlanScreen displayed in the application will be the combination of the two overrides because of the direct relationship. This data inheritance works exactly the same for Plan Fields and Segments used throughout the system.
The data inheritance also functions in a similar way if the relationship between the Product and Plan is indirect. For example, if “Product A” has a direct relationship to “Child Product B” and “Child Product B” has a direct relationship to “Plan A,” but the PlanScreen Business Rule only has overrides for “Product A” and “Plan A,” the PlanScreen that is displayed in the application will be the combination of the two overrides because of the indirect relationship between “Product A” and “Plan A.” Again, this data inheritance works the same for Plan Fields and segments.
Fields are the only aspect of the PlanScreen business rule that are able to utilize data inheritance. There are several important points to consider when configuring a PlanScreen business rule that will be inherited within the Product-Plan structure:
When a field with the same name is present in multiple related overrides, the field will display on the Plan screen in OIPA at highest override level where it's defined. The field will not be able to be moved or deleted by lower-level configuration, only hidden.
The following pieces of segment configuration are able to utilize data inheritance:
See the sections below for detailed information on configuring these aspects of segments when data inheritance is being utilized.
When multiple related segment overrides at the Product, Child Product, and/or Plan level exist with the same name and type, all of the fields configured in the related rules will be displayed in the system UI.
Segment button configuration will not support data inheritance. Each override of the segment will need to define a <Buttons> configuration section. When multiple related overrides of a single segment at the Product, Child Product and/or Plan level have been created, only the buttons configured in the lowest level override will be displayed in the system UI.
Actions sections defined in multiple related overrides of a single segment at the Product, Child Product, and/or Plan level that have unique ActionSet IDs will be combined to form a single Actions section.
If multiple Action sections with the same Action ID are present in related overrides, only the lowest level override’s Action configuration with the ID conflict will be utilized by the system.
The <Events> configuration section can be defined in multiple related overrides of a single segment at the Product, Child Product, and/or Plan level, all of which will be combined to form a single Events section.
If two ONCHANGE Events with the same field specified are present in multiple related overrides, only the lowest level override will be utilized.
The ScreenMath sections defined in multiple related segment overrides at the Product, Child Product, and/or Plan level that have unique Math IDs will be combined to form a single ScreenMath section.
If multiple Math sections with the same Math ID are present in related overrides, only the lowest level override’s Math configuration with the ID conflict will be utilized by the system.
Roles configuration can be defined in multiple related overrides of a single segment at the Product, Child Product, and/or Plan level, and will be combined to form a single roles section.
A role may be hidden using the Hidden configuration setting, but not deleted via a lower-level override's configuration. See the Create a New Segment page for more information on creating and configuring segment roles.
Segment RoleViews configuration that is defined in multiple related overrides of a single segment at the Product, Child Product, and/or Plan level will be combined by the system to form the list of available RoleViews.
Copyright © 2009, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices